home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000268_news@columbia.edu _Mon Feb 17 11:32:10 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA20418
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 17 Feb 1997 11:32:10 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA14585
for kermit.misc@watsun; Mon, 17 Feb 1997 11:32:09 -0500 (EST)
Path: news.columbia.edu!panix!cam-news-hub1.bbnplanet.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!cam-news-feed3.bbnplanet.com!forest!pcoen
From: pcoen@forest.drew.edu (Paul Coen)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: OS/2 Specific DOS and MS-DOS Kermit
Message-ID: <1997Feb17.103511.155285@forest>
Date: 17 Feb 97 10:35:11 EST
References: <1997Feb15.090805.155151@forest> <1997Feb17.100642.26785@lafn.org>
Organization: Drew University Academic Technology
Lines: 55
Xref: news.columbia.edu comp.protocols.kermit.misc:6607
In article <1997Feb17.100642.26785@lafn.org>, aw585@lafn.org (Dallas Legan) writes:
> I went back and added to
> DEVICE=C:\OS2\BOOT\COM.SYS
> to make it:
> DEVICE=C:\OS2\BOOT\COM.SYS (3,3F8,4) (4,2E8,3)
>
Okay, that's good -- I'm sure that wasn't helping matters any. However,
you're using the same IRQ for COM4 as COM2 -- is anything else using
COM2 at the same time? You may need to set COM4 (hardware-wise) to
another IRQ and then change the CONFIG.SYS to match. PC devices can't
share interrupts, with a few exceptions (Microchannel-based PS/2's
from IBM, but even IBM barely makes any MCA machines any longer).
Anyway, you may need to tell MS-Kermit where it is, or where you
put it. The command is 'SET COM4 \x02e8 \3' (or whatever it actually
is).
> and even added the
> DEVICE=C:\OS2\MDOS\COMDD.SYS
> which supposedly some software needs
> (I don't know if I put it in the right position, or
> even if the location in CONFIG.SYS matters?)
>
Order doesn't really matter.
> AAAAAAAAAA-- no, it's not
> it's 3.0
>
RMVIEW should work anyway -- type RMVIEW /? to get the options (I
think they added a few switches in 4.0) -- you can get the IRQ
out of it, and I think the base address.
> Still, why not the Specific DOS?
> (I like the COMMAND.COM that I'm using on it)
> I found that commenting out all COM device drivers
> in CONFIG.SYS - COM.SYS AND VCOM.SYS (and COMDD.SYS if that matters
> any) enabled MS-DOS Kermit to run from a
> Specific DOS session booted from a disk.
> This seems extremely awkward, but maybe it provides someone
> more knowledgable about OS/2 a clue as to what will work more
> smoothly. Somehow, I suspect maybe the VIO.SYS I've seen
> mentioned might solve it, but I don't know.
I think you mean "SIO.SYS" -- VIO is the PM API used to deal with text
windows. The only problem with a "specific DOS" is that it takes
more system overhead. Also, something is just not configured right
if you have to do the above to get it to work -- I've been running
MS-Kermit since OS/2 2.0 in an OS/2 DOS window with no problems.
Anyway, SIO won't help in this situation -- I suspect you'll have the
same sort of configuration problem, whatever it is.